Dispatch events around publishing #598
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@videlalvaro is this something you would consider merging? |
|
@theodormanolescu what do you think about this ? |
theodormanolescu
suggested changes
Mar 16, 2021
| @@ -53,6 +55,7 @@ public function publish($msgBody, $routingKey = '', $additionalProperties = arra | |||
| $msg->set('application_headers', $headersTable); | |||
| } | |||
|
|
|||
| $this->dispatchEvent(BeforePublishingMessageEvent::NAME, new BeforePublishingMessageEvent($this, $msg)); | |||
There was a problem hiding this comment.
Please keep in mind that the signature of the EventDispatcherInterface::dispatch() method has been changed to dispatch($event, string $eventName = null): object since 5.0.0
|
released in #728 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I saw similar requests in #147 and #201 and I wanted this feature to collect more metrics in my application.
Would you consider merging a PR like this?
Of course, we can work more on the details like event names, places etc., I'd just like to know an early answer if it's a no-go.